Method of designing organizational information processing and operational system based upon information providers and information consumers

ABSTRACT

The service function and information design process is automated in order to shorten the design process period. The same process is based upon the relationships between activities and the information that the activities provide and consume. The relationships are maintained in a predetermined format and are updated by any changes that are affecting the relationships. In addition, the activities are further defined by detailed activities.

FIELD OF THE INVENTION

The current invention is generally related to organizational informationprocessing methods and systems, and more particularly related tostandardization and automation in designing a new service operation.

BACKGROUND OF THE INVENTION

In response to globally competitive and ever-changing businessenvironment, many new businesses are now reorganizing their informationsystems that are highly tied to operational strategies. The informationsystems generally function as a foundation for the operation and isdemanded for large-scale, high-speed and complex operations. In additionto the above requirements, it is also strongly demanded that theinformation systems be designed and made ready for use in a short periodof time in the above described highly competitive age. Designing theinformation systems tends to be highly labor intensive and inefficientin the conventional art. To improve the information system designprocess, templates have been used in a limited capacity. For the abovereason, it is highly desirable to improve the process of designinginformation systems.

SUMMARY OF THE INVENTION

In order to solve the above and other problems, according to a firstaspect of the current invention, a method of designing an informationflow process, including the steps of: determining a predetermined set ofactivity names in a predetermined sequence, the activity namesrespectively representing certain service operations; displaying theactivity names as information provider activity names and informationconsumer activity names according to the predetermined sequence in apredetermined data flow definition (DFD) matrix format; specifying aninformation name, one of the information provider activity names and acorresponding one of the information consumer activity names, theinformation name at a position in the predetermined DFD matrix formatrepresenting data to be transmitted from the information provideractivity name to the information consumer activity name; and storing therelations among the information provider activity names, the informationnames and the information consumer activity names in an entity relation(ER) source information file.

According to a second aspect of the current invention, a medium storinga computer program for designing an information flow process, thecomputer program performing the tasks of: determining a predeterminedset of activity names in a predetermined sequence, the activity namesrespectively representing certain service operations; displaying theactivity names as information provider activity names and informationconsumer activity names according to the predetermined sequence in apredetermined data flow definition (DFD) matrix format; specifying aninformation name, one of the information provider activity names and acorresponding one of the information consumer activity names, theinformation name at a position in the predetermined DFD matrix formatrepresenting data to be transmitted from the information provideractivity name to the information consumer activity name; and storing therelations among the information provider activity names, the informationnames and the information consumer activity names in an entity relation(ER) source information file.

These and various other advantages and features of novelty whichcharacterize the invention are pointed out with particularity in theclaims annexed hereto and forming a part hereof. However, for a betterunderstanding of the invention, its advantages, and the objects obtainedby its use, reference should be made to the drawings which form afurther part hereof, and to the accompanying descriptive matter, inwhich there is illustrated and described a preferred embodiment of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a table illustrating an exemplary activity name table to beused in a preferred process of defining information flows that areassociated with operational activities according to the currentinvention.

FIG. 2 is a table illustrating an exemplary data flow definition (DFD)matrix to be used in the preferred process of defining information flowsthat are associated with operational activities according to the currentinvention.

FIG. 3 is a table illustrating an exemplary entity relation (ER) sourceinformation table to be used in the preferred process of defininginformation flows that are associated with operational activitiesaccording to the current invention.

FIG. 4 is a diagram illustrating an exemplary structure data flow chartor input screen to be used in the preferred process of defininginformation flows that are associated with operational activitiesaccording to the current invention.

FIG. 5 is a diagram illustrating an exemplary new service functiondesign table to be used in the preferred process of defining informationflows that are associated with operational activities according to thecurrent invention.

FIG. 6 is a diagram illustrating an exemplary service information designtable to be used in the preferred process of defining information flowsthat are associated with operational activities according to the currentinvention.

FIG. 7 is an exemplary event trace diagram illustrating events in thepreferred process of defining information flows that are associated withoperational activities according to the current invention.

FIG. 8 is a block diagram illustrating a first preferred embodiment ofthe processing unit according to the current invention.

FIG. 9 is a block diagram illustrating a second preferred embodiment ofthe processing unit according to the current invention.

FIG. 10 is a block diagram illustrating a third preferred embodiment ofthe processing unit according to the current invention.

FIG. 11 is a block diagram illustrating a fourth preferred embodiment ofthe processing unit according to the current invention.

FIG. 12 is a block diagram illustrating a fifth preferred embodiment ofthe processing unit according to the current invention.

FIG. 13 is a flow chart illustrating steps involved in the preferredprocess of defining information flows that are associated withoperational activities according to the current invention.

FIG. 14 is a flow chart illustrating further steps involved in thepreferred process of defining information flows that are associated withoperational activities according to the current invention.

FIG. 15 is a flow chart illustrating further steps involved in thepreferred process of defining information flows that are associated withoperational activities according to the current invention.

FIG. 16 is a flow chart illustrating further steps involved in thepreferred process of defining information flows that are associated withoperational activities according to the current invention.

FIG. 17 is a flow chart illustrates further steps involved in thepreferred process of defining information flows that are associated withoperational activities according to the current invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

Referring now to the drawings, wherein like reference numerals designatecorresponding structures throughout the views, and referring inparticular to FIG. 1, a table illustrates an exemplary activity nametable to be used in a preferred process of defining information flowsthat are associated with operational activities according to the currentinvention. The exemplary table maintains activity names for theactivities to be performed by an information provider or an informationconsumer. A first column 301 contains the most detailed activities whilea second column 302 contains a corresponding key value. A third column303 contains mid-level activities that are parent to the detailedactivities in the first column 301. A forth column 304 contains flagsfor indicating the mid-level activities for a data flow definitionmatrix. A fifth column 305 contains flags for indicating a structuredata flow.

FIG. 2, a table illustrates an exemplary data flow definition (DFD)matrix to be used in the preferred process of defining information flowsthat are associated with operational activities according to the currentinvention. The exemplary DFD matrix is used to define activities such asactivities within an information provider and an information consumer aswell as information flows between the information provider and theinformation consumer. The DFD matrix includes an activity name row 201in a horizontal direction, an activity name column 202 in a verticaldirection and an activity name diagonal 203. The activity name row 201maintains from the left to the right the activity names that are storedin the activity name table of FIG. 1 in an ascending manner according tothe key values in the second column 302. Similarly, the activity namecolumn 202 maintains from the top to the bottom the activity names thatare stored in the activity name table of FIG. 1 in an ascending manneraccording to the key values in the second column 302. The activity namediagonal 203 maintains from the top left to the bottom right theactivity names that are stored in the activity name table of FIG. 1 inan ascending manner according to the key values in the second column302. The blank cells in the DFD maintain information names forinformation that is transmitted between the activity names.

Referring to FIG. 3, a table illustrates an exemplary entity relation(ER) source information table to be used in the preferred process ofdefining information flows that are associated with operationalactivities according to the current invention. A first column 401maintains activity names for the information provider. A second column402 maintains information names for the information that the informationprovider provides. A third column 403 maintains activity names for theinformation consumer.

Referring to FIG. 4, a diagram illustrates an exemplary structure dataflow chart or input screen to be used in the preferred process ofdefining information flows that are associated with operationalactivities according to the current invention. An activity name box 501contains an exemplary activity name, “MANUFACTURE” that is to bedetailed. The detail activity name box 502 contains detailed activitynames with respect to input information 503, 504 as well as outputinformation 505, 506. The information provider activity name box 503contains activity names whose activity provide input information to thedetail activity name as stored in the activity name box 501. An inputinformation name box 504 contains information that is provided by thecorresponding activity whose activity name is adjacently placed in theinformation provider activity name box 503. For the detail activity nameas stored in the activity name box 501, an output information name box505 contains information that is used by the corresponding activitywhose activity name is adjacently placed in an information consumeractivity name box 506. The information consumer activity name box 506contains activity names for a common information consumer, and theactivities as specified by the activity names in the informationconsumer activity name box 506 consume the output information.

Referring to FIG. 5, a diagram illustrates an exemplary new servicefunction design table to be used in the preferred process of defininginformation flows that are associated with operational activitiesaccording to the current invention. In general, the new service functiondesign table stores information on service function designs and newfunction descriptions. A first column 601 maintains activity names thatprovide a corresponding information name. A second column 602 maintainsinformation that the above source activity name in the first column 601provides. A third column 603 maintains the activity names that consumethe information stored in the second column 602. A fourth column 604maintains functional systematization factors for the activity names inthe first column 601 that provide the information in the second column602 which in turn is consumed by the activity names in the third column603. A fifth column 605 maintains activity contents for the activitynames in the first column 601 that provide the information in the secondcolumn 602 which in turn is consumed by the activity names in the thirdcolumn 603. Lastly, a sixth column 606 maintains subjects forimplementing the systematization factors in the fourth column 604.

Referring to FIG. 6, a diagram illustrates an exemplary serviceinformation design table to be used in the preferred process of defininginformation flows that are associated with operational activitiesaccording to the current invention. A first column 701 maintainsinformation names. A second column 702 maintains activity names thatprovide information that is stored in the first column 701. A thirdcolumn 703 maintains activity names that consume the information storedin the first column 701. A fourth column 704 maintains informationalsystematization factors for the information names in the first column701 that is provided by the information provider activity names in thefifth column 702 and that is consumed by the activity names in the thirdcolumn 703. A fifth column 705 maintains key items for implementing theinformational systemization factors in the fourth column 704. Lastly, asixth column 706 maintains input items for implementing theinformational systemization factors in the fourth column 704.

Referring to FIG. 7, an exemplary event trace diagram illustrates eventsin the preferred process of defining information flows that areassociated with operational activities according to the currentinvention. The event trace sequentially expresses operational activitiesand informational flows based upon the service operation. A row counterbox 801 stores a number of rows in an event record column 803 for acurrent process. The activity name row 802 maintains from the left tothe right the activity names that are stored in the activity name tableof FIG. 1 in an ascending manner according to the key values in thesecond column 302. The event record column 803 alternatively maintainsthe activity names and the information names from the event trace table.

Now referring to FIG. 8, a block diagram illustrates a first preferredembodiment of the processing unit according to the current invention.The processing unit 1 is connected to an input/output unit 2 and aprinter 5. The processing unit 1 has access to an activity name tablestorage file 3 and an entity relation (ER) source information tablestorage file 4. The processing unit 1 executes a first file input/outputprogram 6 for accessing the activity name table storage file 3, whichstores the activity name table as shown in FIG. 1 and the ER sourceinformation table storage file 4, which stores the ER source informationtable as shown in FIG. 3. The processing unit 1 executes a data flowdefinition (DFD) matrix data screen input/output program 8 for inputtingand outputting data via the input/output unit 2 to and from theprocessing unit 1. The input/output unit 2 displays DFD matrix data orreceives the data for a DFD matrix. Based upon the information from theactivity name table storage file 3 and the ER source information tablestorage file 4 via the first file input/output program 6, the processingunit 1 executes a DFD generation program 7 for generating a DFD matrixas shown in FIG. 2 and for outputting the generated DFD matrix to a DFDmatrix output program 9. The DFD matrix data screen input/output program8 receives the generated DFD matrix from the DFD generation program 7and outputs to the input/output unit 2. The DFD matrix data screeninput/output program 8 and the DFD generation program 7 receive someinput data from the input/output unit 2 and place the data at acorresponding position in the generated DFD matrix. Finally, theprocessing unit 1 executes the DFD matrix output program 9 foroutputting the DFD matrix to the printer 5.

Now referring to FIG. 9, a block diagram illustrates a second preferredembodiment of the processing unit according to the current invention.The processing unit 10 is connected to an input/output unit 2 and aprinter 5. The processing unit 10 has access to the activity name tablestorage file 3 and the entity relation (ER) source information tablestorage file 4. The processing unit 10 executes the first fileinput/output program 6 for accessing the activity name table storagefile 3, which stores the activity name table as shown in FIG. 1 and theER source information table storage file 4, which stores the ER sourceinformation table as shown in FIG. 3. The processing unit 10 executes astructured data flow (SDF) data screen input/output program 12 forinputting and outputting data via the input/output unit 2 to and fromthe processing unit 10. The input/output unit 2 displays SDF data orreceives the data for a SDF chart. Based upon the information from theactivity name table storage file 3 and the ER source information tablestorage file 4 via the first file input/output program 6, the processingunit 10 executes a SDF generation program 11 for generating a SDF chartas shown in FIG. 4 and for outputting the generated SDF chart to a SDFoutput program 13. The DFD matrix data screen input/output program 8receives the generated DFD matrix from the SFD generation program 11 andoutputs to the input/output unit 2. The SDF data screen input/outputprogram 12 and the SDF generation program 11 receive some input datafrom the input/output unit 2 and place the data at a correspondingposition in the generated SDF chart. Finally, the processing unit 10executes the SDF output program 13 for outputting the SDF chart to theprinter 5.

Now referring to FIG. 10, a block diagram illustrates a third preferredembodiment of the processing unit according to the current invention.The processing unit 14 is connected to an input/output unit 2 and aprinter 5. The processing unit 14 has access to the activity name tablestorage file 3, the entity relation (ER) source information tablestorage file 4 as well as a service function design/new functiondescription table storage file 15. The processing unit 14 executes thefirst file input/output program 6 for accessing the activity name tablestorage file 3, which stores the activity name table as shown in FIG. 1and the ER source information table storage file 4, which stores the ERsource information table as shown in FIG. 3. The processing unit 14executes a second file input/output program 16 for accessing theactivity name table storage file 15, which stores the new servicefunction design table as shown in FIG. 5. The processing unit 14executes a function items systematization factors screen input/outputprogram 18 for inputting and outputting data via the input/output unit 2to and from the processing unit 14. The input/output unit 2 displaysdata or receives the data for new function description. Based upon theinformation from the activity name table storage file 3 and the ERsource information table storage file 4 via the first file input/outputprogram 6 as well as from the activity name table storage file 15 viathe second file input/output program 16, the processing unit 14 executesa new function description generation program 17 for generating the newfunction description and for outputting the generated new functiondescription to a new function description output program 19. Thefunction items systematization factors screen input/output program 18receives the generated new function description from the new functiondescription generation program 17 and outputs the new functiondescription to the input/output unit 2. The function itemssystematization factors screen input/output program 18 and the newfunction description generation program 17 receive some input data fromthe input/output unit 2 and place the data at a corresponding positionin the new function description. Finally, the processing unit 14executes the new function description output program 19 for outputtingthe new function description to the printer 5.

Now referring to FIG. 11, a block diagram illustrates a fourth preferredembodiment of the processing unit according to the current invention.The processing unit 20 is connected to an input/output unit 2 and aprinter 5. The processing unit 20 has access to the activity name tablestorage file 3, the entity relation (ER) source information tablestorage file 4 as well as a service information design input/outputinformation overview table storage file 21. The processing unit 20executes the first file input/output program 6 for accessing theactivity name table storage file 3, which stores the activity name tableas shown in FIG. 1 and the ER source information table storage file 4,which stores the ER source information table as shown in FIG. 3. Theprocessing unit 20 executes a third file input/output program 22 foraccessing the service information design input/output informationoverview table storage file 21, which stores the service informationdesign table as shown in FIG. 6 and an input/output information overviewtable. The processing unit 20 executes an information itemssystematization screen input/output program 24 for inputting andoutputting data via the input/output unit 2 to and from the processingunit 20. The input/output unit 2 displays data or receives the data forthe input/output information overview. Based upon the information fromthe activity name table storage file 3 and the ER source informationtable storage file 4 via the first file input/output program 6 as wellas from the service information design input/output information overviewtable storage file 21 via the third file input/output program 22, theprocessing unit 20 executes an input/output information generationprogram 23 for generating the input/output information overview and foroutputting the generated input/output information overview to aninput/output information overview output program 25. The informationitems systematization factor screen input/output program 24 receives thegenerated input/output information overview from the input/outputinformation overview generation program 23 and outputs the input/outputinformation overview to the input/output unit 2. The information itemssystematization factor screen input/output program 24 and theinput/output information overview generation program 23 receive someinput data from the input/output unit 2 and place the data at acorresponding position in the input/output information overview.Finally, the processing unit 20 executes the input/output informationoverview output program 25 for outputting the input/output informationoverview to the printer 5.

Now referring to FIG. 12, a block diagram illustrates a fifth preferredembodiment of the processing unit according to the current invention.The processing unit 26 is connected to an input/output unit 2 and aprinter 5. The processing unit 26 has access to the activity name tablestorage file 3, the entity relation (ER) source information tablestorage file 4 as well as an event trace data table storage file 27. Theprocessing unit 26 executes the first file input/output program 6 foraccessing the activity name table storage file 3, which stores theactivity name table as shown in FIG. 1 and the ER source informationtable storage file 4, which stores the ER source information table asshown in FIG. 3. The processing unit 26 executes a fourth fileinput/output program 28 for accessing the event trace data table storagefile 27, which stores event trace data. The processing unit 26 executesan event trace data screen input/output program 30 for inputting andoutputting data via the input/output unit 2 to and from the processingunit 26. The input/output unit 2 displays data or receives the data fora correspond DFD matrix.

Based upon the information from the activity name table storage file 3and the ER source information table storage file 4 via the first fileinput/output program 6 as well as from the event trace data tablestorage file 27 via the fourth file input/output program 28, theprocessing unit 26 executes an event trace diagram generation program 29for generating the event trace diagram and for outputting the generatedevent trace diagram to an event trace diagram output program 31. Theevent trace data screen input/output program 30 receives the generatedevent trace diagram from the event trace diagram generation program 29and outputs the event trace diagram to the input/output unit 2. Theevent trace data screen input/output program 30 and the event tracediagram generation program 29 receive some input data from theinput/output unit 2 and place the data in the event trace table.Finally, the processing unit 26 executes the event trace diagram outputprogram 31 for outputting the event trace diagram to the printer 5.

Referring to FIG. 13, a flow chart illustrates steps involved in thepreferred process of defining information flows that are associated withoperational activities according to the current invention. Inparticular, the steps are performed by the DFD generation program 7. Viathe input/output unit 2, an activity name is inputted into the firstcolumn 301 of the activity name table as shown in FIG. 1 and is storedin the activity name table storage file 3 in a step 101. Subsequently, aclassification key that indicates an activity name order is inputtedinto the second column 302 of the activity name table in a step 102. Ina step 103, the above stored activity name is read into a blank DFDmatrix from the first column 301 in the activity name table in theactivity name table storage file 3. The reading sequence is according tothe ascending order of the classification key in the second column 302of the activity name table as shown in FIG. 1. For a horizontal axis,the reading sequence of the activity names is from the left to theright. For a vertical axis, the reading sequence of the activity namesis from the top to the bottom. For a diagonal direction, the readingsequence of the activity names is from the top left to the bottom rightwhere the same activity names cross from horizontal and vertical axes.In a step 104, it is confirmed with a user whether or not informationnames are inputted in the DFD matrix. If there is no need to input theinformation names, the preferred process proceeds to a step 107. On theother hand, if the information names are to be inputted, in a step 105,the information name that is consumed by the activity name on thevertical axis and that is provided by the activity name on thehorizontal axis is placed via the input/output unit 2 in a correspondingcell or position where the above activity names cross in the DFD matrix.

Still referring to FIG. 13, the information provider activity name, thecorresponding information name and the information consumer are storedrespectively in the first column 401, the second column 402 and thethird column 403 in the entity relation (ER) source information table asshown in FIG. 3 in a step 106. In a step 107, it is confirmed with theuser whether or not there is a level specification for the activity nameto be displayed in the DFD matrix. When a level is specified and thespecified level is the mid-level, a flag is inserted in the fourthcolumn 304 of the activity name table as shown in FIG. 1 in a step 108.On the other hand, when there is no level specification, the preferredprocess proceeds to a step 109, where the detailed activity names in thefirst column 301 of the activity name table as shown in FIG. 1 are usedto display in the DFD matrix as shown in FIG. 2. In the step 109, whenthe level specification flag in the third column 304 is “1,” themid-level activity names are used to display in the DFD matrix. In otherwords, depending upon the flag in the fourth column 304 of the activityname table, either the activity name in the first column 301 or theactivity name in the third column 303 is displayed in the DFD matrix.

Subsequently, a series of questions is asked to the user. In a step 110,it is confirmed with the user whether or not there is a change in theinformation name or the position. If there is a change, the preferredprocess goes back the step 105. On the other hand, if there is nochange, it is further confirmed with the user whether or not there is achange in the activity name sequence in a step 111. If there is achange, the preferred process goes back the step 102. On the other hand,if there is no change, it is further confirmed with the user whether ornot there is a change in the activity name sequence in a step 111. Ifthere is a change, the preferred process goes back the step 102 forchanging the classification key according to the modified sequence. Onthe other hand, if there is no change, it is further confirmed with theuser whether or not there is a change in the activity name in a step112. If there is a change, the preferred process goes back the step 101for inputting the activity name change. On the other hand, if there isno change, the user is asked whether or not she wishes to print the DFDmatrix in a step 113. If printing is desired, the DFD matrix as shown inFIG. 2 is printed via the printer 5 in a step 114. If no printing isdesired, the preferred process bypasses the step 114.

Referring to FIG. 14, a flow chart illustrates further steps involved inthe preferred process of defining information flows that are associatedwith operational activities according to the current invention. Inparticular, the steps are performed by the SDF generation program 11.The following steps are either independent from or continuous with theprevious steps as shown in FIG. 13. The user is asked whether or not shewishes to generate the SDF in a step 115. If the user specifies that SDFis not generated, the preferred process skips steps 116 through 126 andpotentially continues to a step 127 in FIG. 15. On the other hand, ifthe user selects to generate SDF, the activity name table is read infrom the activity name table storage file 3 in a step 116. In theactivity name table, another flag is indicated in the fifth column 305for the corresponding activity name in the first column 301 to be usedfor generating SDF in a step 117. The activity name as indicated by theflag in the fifth column 305 is searched in the ER source informationtable in the ER source information table storage file 4 in a step 118.

In a step 119, the above flagged activity name is placed in the activitybox 501. If the above flagged activity name is in the first column 401in the ER source information table, the above flagged activity name isan information provider. Because of the information provider status, theinformation name in the second column 402 in the ER source informationtable is outputted to the output information name box 505 in the SDFchart as shown in FIG. 4. Similarly, the information consumer activityname in the third column 403 in the ER source information table isoutputted to the information consumer box 506 in the SDF chart as shownin FIG. 4. On the other hand, if the above flagged activity name is inthe third column 403 in the ER source information table, the aboveflagged activity name is an information consumer. Because of theinformation consumer status, the information name in the second column402 in the ER source information table is outputted to the inputinformation name box 504 in the SDF chart as shown in FIG. 4. Theinformation provider activity name corresponding to the activity name inthe first column 401 in the ER source information table is placed in theinformation provider activity name box 503. Finally, the SDF chart isgenerated and is outputted to the input/output unit 2 in the step 119.

Still referring to FIG. 14, in a step 120, the activity name asdisplayed in the activity name box 501 in the above generated SDF chartis further detailed by inputting the corresponding detailed activitynames in the detailed activity name column 502. The detailed activityname includes the input information corresponding to the informationprovider activity name box 503 and the input information name box 504and the output information corresponding to the information consumeractivity name box 5036 and the output information name box 505. In astep 121, the activity name in the first column 301 in the activity nametable that corresponds to the activity name in the activity name box 501in the SDF chart is replaced by one or more of the detailed activitynames that are placed in the detailed activity name box 502 in the SDFchart. Prior to the above replacement, the above activity names arecopied in the corresponding third column 303 of the activity name tableas shown in FIG. 3. In a step 122, based upon the corresponding relationbetween the information name in the input information name box 504 inthe SDF chart and the information name in the second column 402 in theER source information table, the information consumer activity name inthe third column 403 of the ER source information table is changed tothe detailed activity name in the detailed activity name box 502 of theSDF chart. Similarly, in the step 122, based upon the correspondingrelation between the information name in the output information name box505 in the SDF chart and the information name in the second column 402in the ER source information table, the information provider activityname in the first column 401 of the ER source information table ischanged to the detailed activity name in the detailed activity name box502 of the SDF chart. Thus, the ER source information table has beenupdated in the step 122. It is confirmed with the user whether or notthe SDF chart is to be printed in a step 123. If it is desired forprinting, the SDF chart as shown in FIG. 5 is outputted to the printer 5in a step 124. Subsequent to the step 124 or if no printing is desiredin the step 123, it is further confirmed with the use whether or not adetailed DFD matrix is to be generated based upon the detailed activitynames in a step 125. If the detailed DFD matrix is to be generated, thepreferred process returns to the step 109 via a step 126. On the otherhand, if the detailed DFD matrix is not to be generated, the preferredprocess proceeds to a step 127 in FIG. 15 as indicated by the letter B.

Referring to FIG. 15, a flow chart illustrates further steps involved inthe preferred process of defining information flows that are associatedwith operational activities according to the current invention. Inparticular, the steps are performed by the new function descriptiongeneration program 17. The following steps are either independent fromor continuous with the previous steps as shown in FIG. 14. In a step127, it is confirmed with the user whether or not new functiondescription is to be generated. If the new function description is notgenerated, the preferred process skips steps 127 through 134 to proceedto a step 135 as shown in FIG. 16. On the other hand, if the newfunction description is generated, the information provider activityname in the first column 401, the information name in the second column402 and the information consumer activity name in the third column 403of the ER source information table are respectively copied into thefirst column 601, the second column 602 and the third column 603 of thenew service function table in the service function design/new functiondescription table storage file 15 and are outputted to the input/outputunit 2 in a step 128. In the above duplication, the information for theactivity names in the first column 601 in the new service function tableis placed in the vertical direction according to the sequence asindicated by the classification key in the second column 302 of theactivity name table in the step 128.

Still referring to FIG. 15, in a step 129, it is confirmed with the userwhether or not the user refers to the service information design tableas shown in FIG. 6. If the service information design table does not yetexist or the user does not wish to refer to it, the preferred processproceeds to a step 132. On the other hand, if the service informationdesign table is to be referred, a combination of the first, second andthird columns 601, 602, 603 is selected in a step 130. The selectedcombination is searched in the first, second and third columns 701, 702,703 in the service information design table, and the searched resultsare displayed in a step 131. The above reference on the informationallows the user to consider functional systematization factors.Subsequently, the preferred process returns to the step 128, where theservice function design table is again displayed and to the step 129,where the user is asked whether or not the service information designtable needs to be referred. If there is no need for the reference, in astep 132, the input/output unit 2 reads the systematization factors, theactivity contents and the subject from the fourth, fifth and sixthcolumns 604, 605 and 606 of the service function table and stores themin a new function description table in the service information designinput/output information overview table storage file 21. In a step 133,the user is asked whether or not the new function description is to beprinted. If the new function description is to be printed, the newfunction description is outputted to the printer 5 in a step 134. On theother hand, if the new function description is not printed, thepreferred process proceeds to the step 135 as shown in FIG. 16.

Referring to FIG. 16, a flow chart illustrates further steps involved inthe preferred process of defining information flows that are associatedwith operational activities according to the current invention. Inparticular, the steps are performed by the input/output informationoverview generation program 23. The following steps are eitherindependent from or continuous with the previous steps as shown in FIG.15. In addition, if they are continuous, the orders of the steps asshown in FIG. 15 and 16 are optionally reversed. In a step 135, it isconfirmed with the user whether or not an input/output informationoverview is to be generated. If the input/output information overview isnot generated, the preferred process skips steps 136 through 142 toproceed to a step 143 as shown in FIG. 17. On the other hand, if theinput/output information overview is generated, the information provideractivity name in the first column 401, the information name in thesecond column 402 and the information consumer activity name in thethird column 403 of the ER source information table are respectivelycopied into the first column 701, the second column 702 and the thirdcolumn 703 of the service information design table in in the serviceinformation design input/output information overview table storage file21 and are outputted to the input/output unit 2 in a step 136. In theabove duplication, the information for the activity names in the firstcolumn 701 in the service information table is placed in the verticaldirection according to the sequence as indicated by the classificationkey in the second column 302 of the activity name table in the step 136.

Still referring to FIG. 16, in a step 137, it is confirmed with the userwhether or not the user refers to the service function design table asshown in FIG. 5. If the service function design table does not yet existor the user does not wish to refer to it, the preferred process proceedsto a step 140. On the other hand, if the service function design tableis to be referred, a combination of the first, second and third columns701, 702, 703 is selected in a step 138. The selected combination issearched in the first, second and third columns 601, 602, 603 in theservice function design table, and the searched results are displayed ina step 139. The above reference on the information allows the user toconsider functional systematization factors. Subsequently, the preferredprocess returns to the step 136, where the service function design tableis again displayed and to the step 137, where the user is asked whetheror not the service function design table needs to be referred. If thereis no need for the reference, in a step 140, the input/output unit 2reads the systematization factors, the key items and the input itemsfrom the fourth, fifth and sixth columns 704, 705 and 706 of the serviceinformation design table and stores them in an input/output informationoverview table in the service information design input/outputinformation overview table storage file 21. In a step 141, the user isasked whether or not the input/output information overview is to beprinted. If the input/output information overview is to be printed, theinput/output information overview is outputted to the printer 5 in astep 142. On the other hand, if the input/output information overview isnot printed, the preferred process proceeds to the step 143 as shown inFIG. 17.

Referring to FIG. 17, a flow chart illustrates further steps involved inthe preferred process of defining information flows that are associatedwith operational activities according to the current invention. Inparticular, the steps are performed by the event trace diagramgeneration program 29. The following steps are either independent fromor continuous with the previous steps as shown in FIG. 16. In a step143, it is confirmed with a user whether or not an event trace chart isgenerated. If the event trace chart is not generated, the preferredprocess skips steps 144 through 157 and terminates. On the other hand,if the event trace is to be generated, the DFD matrix as shown in FIG. 2is displayed based upon the activity name table and the ER sourceinformation table in a step 144. The activity names and the informationnames are alternatively sequentially selected from the DFD matrixaccording to the service operation. The above selection starts with anactivity name and ends with another activity name in a step 145. Theselected activity names and information names are stored in the eventtrace table in a step 146. In a step 147, it is confirmed whether or notthe user has finished selecting the activity names and the informationnames. If it is determined that the selection has not completed in thestep 147, the preferred process returns to the step 145. On the otherhand, if it is determined that the selection has completed in the step147, the line counter as indicated in the counter box 801 of the eventtrace is initialized in a step 148. In a step 149, the activity names inthe first column 301 in the activity name table are expanded as shown inFIG. 7 from the left to the right in the activity name row 802 in theevent trace chart according to the ascending sequence specifies by theclassification key in the second column of the activity name table. Oneof the activity names is read from the event trace table for the eventtrace diagram, and the activity name is placed in the event recordcolumn 803 in a step 150. The same activity name is searched in theactivity name row 802 in the step 150. In a step 151, the nextinformation name after the current activity name is displayed in theevent record column 803 that corresponds to the line counter box 801 andthe row that corresponds to the activity name row 802 in the searchedevent trace table. Subsequently, the next activity name is read from theevent trace table and is stored in the event record column 803 in theevent trace diagram as shown in FIG. 7 in a step 152. The informationname in the corresponding row of the activity name row 802 is connectedto the current activity name in the event record column 803 by a line ina step 153. The line counter is incremented in a step 154. It isconfirmed with the user whether or not the selected activity name is thelast one in the event trace table in a step 155. If it is determinedthat the activity name is not the last one, the preferred processreturns to the step 150. On the other hand, if it is determined that theactivity name is the last one, the user is asked whether or not theevent trace diagram is to be printed in a step 156. If the user wishesto print the event trace diagram, the event trace diagram as shown inFIG. 7 is outputted to the printer 5. On the other hand, if the userwishes not to print the event trace diagram, the preferred process ends.

The above described preferred processes and preferred embodiments enablethe new service design process to be automated or standardized. The newservice design process is shortened. While the clients befit from theshort design period, the designers also benefit from the reduced designsteps. Furthermore, since the design process is electronicallycumulative, the know-how is also cumulated by sharing the commonknowledge as well as improves the internal efficiency by transmittingthe design information.

It is to be understood, however, that even though numerouscharacteristics and advantages of the present invention have been setforth in the foregoing description, together with details of thestructure and function of the invention, the disclosure is illustrativeonly, and that although changes may be made in detail, especially inmatters of shape, size and arrangement of parts, as well asimplementation in software, hardware, or a combination of both, thechanges are within the principles of the invention to the full extentindicated by the broad general meaning of the terms in which theappended claims are expressed.

1. A method of designing an information flow process, comprising thesteps of: determining a predetermined set of activity names in apredetermined sequence, the activity names respectively representingcertain service operations; displaying the activity names as informationprovider activity names and information consumer activity namesaccording to the predetermined sequence in a predetermined data flowdefinition (DFD) matrix format; specifying an information name, one ofthe information provider activity names and a corresponding one of theinformation consumer activity names, the information name at a positionin the predetermined DFD matrix format representing data to betransmitted from the information provider activity name to theinformation consumer activity name; storing the relations among theinformation provider activity names, the information names and theinformation consumer activity names in an entity relation (ER) sourceinformation file; further determining associated detailed activities ofa selected one of the activity names; updating the predetermined DFDmatrix format based upon the associated detailed activities fordisplaying the activity names; and storing the activity names with theassociated detailed activities in the ER source information file.
 2. Themethod of designing an information flow process according to claim 1further comprising additional steps of: modifying the activity names;and updating said displaying of the activity names in the predeterminedDFD matrix format; and storing the modified activity names in the ERsource information file.
 3. The method of designing an information flowprocess according to claim 1 further comprising additional steps of:modifying the predetermined sequence for the activity names; andupdating said displaying the activity names in the predetermined DFDmatrix format according to the modified predetermined sequence; andstoring the modified predetermined sequence of the activity names in theER source information file.
 4. The method of designing an informationflow process according to claim 1 further comprising additional stepsof: modifying the information names; and updating said displaying of theinformation names in the predetermined DFD matrix format; and storingthe modified information names in the ER source information file.
 5. Themethod of designing an information flow process according to claim 1further comprising additional steps of: modifying the positions of theinformation names; and updating said displaying the information names inthe predetermined DFD matrix format at the modified positions; andstoring the modified positions of the information names in the ER sourceinformation file.
 6. The method of designing an information flow processaccording to claim 1 further comprising additional steps of: furtherdetermining associated detailed activities of a selected one of theactivity names; updating said displaying the activity names in thepredetermined DFD matrix format based upon the associated detailedactivities; and storing the activity names with the associated detailedactivities in the ER source information file.
 7. The method of designingan information flow process according to claim 6 wherein said furtherdetermining step additionally includes the steps of: preparing astructure data flow (SDF) input screen based upon the ER sourceinformation file; and receiving user input data for the associateddetailed activities via the SDF input screen.
 8. The method of designingan information flow process according to claim 7 wherein the SDF inputscreen displays an information provider activity name, an inputinformation name, a detailed activity name, an output information nameand an information consumer activity name.
 9. The method of designing aninformation flow process according to claim 1 further comprisingadditional steps of: displaying a service function design table basedupon information from the ER source information file, the servicefunction design table allowing a user to define a new service function;receiving user input data at least for systematization factors; andstoring the systematization factors and the information in the servicefunction design table as a new function description.
 10. The method ofdesigning an information flow process according to claim 9 wherein theuser input data includes activity contents and subjects.
 11. The methodof designing an information flow process according to claim 9 furthercomprising an additional step of printing the new function description.12. The method of designing an information flow process according toclaim 1 further comprising additional steps of: displaying a serviceinformation design table based upon information from the ER sourceinformation file, the service information design table allowing a userto define new service information; receiving user input data at leastfor systematization factors; and storing the systematization factors andthe information in the service information design table as aninput/output information overview.
 13. The method of designing aninformation flow process according to claim 12 wherein the user inputdata includes activity contents and subjects.
 14. The method ofdesigning an information flow process according to claim 12 furthercomprising an additional step of printing the input/output informationoverview.
 15. The method of designing an information flow processaccording to claim 1 further comprising additional steps of: selectingsequential pairs of the activity names and the information names fromthe DFD matrix; storing the sequential pairs of the activity names andthe information names into an event trace table; reading one of theactivity names from the event trace table; displaying the one of theactivity names in an event record column in an event trace diagram;reading a corresponding one of the information names from the eventtrace; and displaying the corresponding one of the information names ina row that corresponds to the one of the activity names in the eventrecord column.
 16. The method of designing an information flow processaccording to claim 15 further comprising an additional step of printingthe event trace diagram.
 17. A medium storing a computer program fordesigning an information flow process, the computer program performingthe tasks of: determining a predetermined set of activity names in apredetermined sequence, the activity names respectively representingcertain service operations; displaying the activity names as informationprovider activity names and information consumer activity namesaccording to the predetermined sequence in a predetermined data flowdefinition (DFD) matrix format; specifying an information name, one ofthe information provider activity names and a corresponding one of theinformation consumer activity names, the information name at a positionin the predetermined DFD matrix format representing data to betransmitted from the information provider activity name to theinformation consumer activity name; storing the relations among theinformation provider activity names, the information names and theinformation consumer activity names in an entity relation (ER) sourceinformation file; receiving additional user input data for selectingsequential pairs of the activity names and the information names fromthe DFD matrix; storing the sequential pairs of the activity names andthe information names into an event trace table; reading one of theactivity names from the event trace table; displaying the one of theactivity names in an event record column in an event trace diagram;reading a corresponding one of the information names from the eventtrace; and displaying the corresponding one of the information names ina row that corresponds to the one of the activity names in the eventrecord column.
 18. The medium storing a computer program for designingan information flow process according to claim 17 further performingadditional tasks of: modifying the activity names; and updating saiddisplaying of the activity names in the predetermined DFD matrix format;and storing the modified activity names in the ER source informationfile.
 19. The medium storing a computer program for designing aninformation flow process according to claim 17 further performingadditional tasks of: modifying the predetermined sequence for theactivity names; and updating said displaying the activity names in thepredetermined DFD matrix format according to the modified predeterminedsequence; and storing the modified predetermined sequence of theactivity names in the ER source information file.
 20. The medium storinga computer program for designing an information flow process accordingto claim 17 further performing additional tasks of: modifying theinformation names; and updating said displaying of the information namesin the predetermined DFD matrix format; and storing the modifiedinformation names in the ER source information file.
 21. The mediumstoring a computer program for designing an information flow processaccording to claim 17 further performing additional tasks of: modifyingthe positions of the information names; and updating said displaying theinformation names in the predetermined DFD matrix format at the modifiedpositions; and storing the modified positions of the information namesin the ER source information file.
 22. The medium storing a computerprogram for designing an information flow process according to claim 17further performing additional tasks of: further determining associateddetailed activities of a selected one of the activity names; updatingsaid displaying the activity names in the predetermined DFD matrixformat based upon the associated detailed activities; and storing theactivity names with the associated detailed activities in the ER sourceinformation file.
 23. The medium storing a computer program fordesigning an information flow process according to claim 22 wherein saidfurther determining task additionally includes the tasks of: preparing astructure data flow (SDF) input screen based upon the ER sourceinformation file; and receiving user input data for the associateddetailed activities via the SDF input screen.
 24. The medium storing acomputer program for designing an information flow process according toclaim 23 wherein the SDF input screen displays an information provideractivity name, an input information name, a detailed activity name, anoutput information name and an information consumer activity name. 25.The medium storing a computer program for designing an information flowprocess according to claim 17 further performing additional tasks of:displaying a service function design table based upon information fromthe ER source information file, the service function design tableallowing a user to define a new service function; receiving user inputdata at least for systematization factors; and storing thesystematization factors and the information in the service functiondesign table as a new function description.
 26. The medium storing acomputer program for designing an information flow process according toclaim 25 wherein the user input data includes activity contents andsubjects.
 27. The medium storing a computer program for designing aninformation flow process according to claim 25 further comprising anadditional task of printing the new function description.
 28. The mediumstoring a computer program for designing an information flow processaccording to claim 17 further comprising additional tasks of: displayinga service information design table based upon information from the ERsource information file, the service information design table allowing auser to define new service information; receiving user input data atleast for systematization factors; and storing the systematizationfactors and the information in the service information design table asan input/output information overview.
 29. The medium storing a computerprogram for designing an information flow process according to claim 28wherein the user input data includes activity contents and subjects. 30.The medium storing a computer program for designing an information flowprocess according to claim 28 further comprising an additional step ofprinting the input/output information overview.
 31. The medium storing acomputer program for designing an information flow process according toclaim 17 further comprising additional tasks of: selecting sequentialpairs of the activity names and the information names from the DFDmatrix; storing the sequential pairs of the activity names and theinformation names into an event trace table; reading one of the activitynames from the event trace table; displaying the one of the activitynames in an event record column in an event trace diagram; reading acorresponding one of the information names from the event trace; anddisplaying the corresponding one of the information names in a row thatcorresponds to the one of the activity names in the event record column.32. The medium storing a computer program for designing an informationflow process according to claim 31 further comprising an additional taskof printing the event trace diagram.